concurrent transaction造句
例句与造句
- Exclusive locks prevent access to a resource by concurrent transactions
排他锁（ x锁）可以防止并发事务对资源进行访问。 - Shared locks allow concurrent transactions to read select a resource under pessimistic concurrency control
共享锁（ s锁）允许并发事务在封闭式并发控制（请参阅 - Conversely , a query holding a sch - s lock blocks a concurrent transaction that attempts to acquire a sch - m lock
相反，持有sch - s锁的查询将阻塞尝试获取sch - m锁的并发事务。 - When one transaction holds a lock on an item , no concurrent transaction can read and / or modify this item
当一个事务对一个数据拥有了锁，那么其他并发事务则无法对它进行读或者写。 - Because of this , queries are blocked when a concurrent transaction holds a sch - m schema modification lock on the table
因此，当并发事务持有表的sch - m （架构修改）锁时，将阻塞查询。 - It's difficult to find concurrent transaction in a sentence. 用concurrent transaction造句挺难的
- A transaction is a unit of isolation and each occurs separately and independently of concurrent transactions
事务是一个隔离单元，并发事务中的每个事务在发生时都相互分离，彼此独立。 - Modifications made by concurrent transactions must be isolated from the modifications made by any other concurrent transactions
由并发事务所作的修改必须与任何其他并发事务所作的修改隔离。 - Imagine that two concurrent transactions both read a row , one writes to it and commits , and then the second writes to it and commits
有两个并发事务同时读取同一行数据，然后其中一个对它进行修改提交，而另一个也是修改提交。 - In addition , it brings forward the method to the concurrent transactions " s cooperative process , solve the underlying conflication problems
另外,在协议栈的实现过程中,对多个并发事务的协调处理提出了自己的解决思路,有效地克服了潜在的会话冲突问题。 - The microsoft sql server database engine locks resources using different lock modes that determine how the resources can be accessed by concurrent transactions
Microsoft sql server数据库引擎使用不同的锁模式锁定资源，这些锁模式确定了并发事务访问资源的方式。 - If a lock escalation attempt fails because of conflicting locks held by concurrent transactions , the database engine will retry the lock escalation for each additional 1 , 250 locks acquired by the transaction
如果由于并发事务所持有的锁冲突而导致锁升级尝试失败，则数据库引擎将对事务获取的其他1 , 250个锁重试锁升级。 - A transaction either recognizes data in the state it was in before another concurrent transaction modified it , or it recognizes the data after the second transaction has completed , but it does not recognize an intermediate state
事务识别数据时数据所处的状态，要么是另一并发事务修改它之前的状态，要么是第二个事务修改它之后的状态，事务不会识别中间状态的数据。 - This isolation level eliminates the possibility that one transaction could overwrite changes made by another concurrent transaction ( the second lost updates problem ) if all data access is performed in a single atomic database transaction
如果所有的数据访问都是在统一的原子数据库事务中，此隔离级别将消除一个事务在另外一个并发事务过程中覆盖数据的可能性（第二个事务更新丢失问题） 。 - The following example uses a test scenario in which four concurrent transactions , each identified by a transaction sequence number , are running in a database that has the allow snapshot isolation and read committed snapshot options set to on
下面的示例使用具有四个并发事务的测试方案，每一个事务都由事务序列号( xsn )标识，并在allow _ snapshot _ isolation和read _ committed _ snapshot选项设置为on的数据库中运行。 - The performance and capability requirements expected for wireless location - based service can easily approach that of heavily used applications ? that is , millions of queries on a daily basis , hundreds of concurrent transactions , and millisecond query - response times
基于位置的无线服务的预期性能和容量很容易就能达到使用量很大的应用程序所提出的要求? ?也就是每天进行上百万次的查询，同时进行上百个交易和毫秒级查询响应时间。